Secondary memory to store error correction information

ABSTRACT

A system and method are disclosed in which a first non-volatile memory includes blocks that store data, and a second memory that stores error correction information related to the blocks storing the data. The first memory and the second memory are of different types.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No. 12/346,015, filed Dec. 30, 2008 which is incorporated in its entirety by reference herein.

BACKGROUND

1. Field of the Application

Subject matter disclosed herein may relate to non-volatile memory, and may relate in particular to improving the reliability or extending the useful life of a non-volatile memory device, for example.

2. Description of the Related Art

Non-volatile memory devices, including Flash memory devices, may be found in a wide range of electronic devices. In particular, Flash memory devices may be used in computers, digital cameras, cellular telephones, personal digital assistants, etc. Flash memories may be embedded in the devices, or may be incorporated into portable solid-state storage devices. As Flash memories continue to increase in storage capacity, and as storage cell geometries decrease, issues related to error correction/detection and device longevity may become more prominent.

BRIEF DESCRIPTION OF THE DRAWINGS

Claimed subject matter is particularly pointed out and distinctly claimed in the concluding portion of the specification. However, both as to organization and/or method of operation, together with objects, features, and/or advantages thereof, it may best be understood by reference to the following detailed description if read with the accompanying drawings in which:

FIG. 1 is a block diagram of an example embodiment of a solid-state storage device;

FIG. 2 is a block diagram depicting an example embodiment of a computing platform;

FIG. 3 is a diagram depicting an example embodiment of a secondary memory containing error correction information related to information stored in a primary non-volatile memory;

FIG. 4 is a flow diagram of an example embodiment of a method for storing, in a secondary memory, error correction information related to information stored in a primary non-volatile memory;

FIG. 5 is a diagram depicting an example embodiment of a secondary memory containing error correction information related to information stored in a primary non-volatile memory; and

FIG. 6 is a block diagram of an example embodiment of a secondary memory containing wear-leveling information related to blocks of storage locations in a primary memory.

DETAILED DESCRIPTION

Reference is made in the following detailed description to the accompanying drawings, which form a part hereof, wherein like numerals may designate like parts throughout to indicate corresponding or analogous elements. It will be appreciated that for simplicity and/or clarity of illustration, elements illustrated in the figures have not necessarily been drawn to scale. For example, the dimensions of some of the elements may be exaggerated relative to other elements for clarity. Further, it is to be understood that other embodiments may be utilized. Furthermore, structural or logical changes may be made without departing from the scope of claimed subject matter. It should also be noted that directions or references, for example, up, down, top, bottom, and so on, may be used to facilitate discussion of the drawings and are not intended to restrict the application of claimed subject matter. Therefore, the following detailed description is not to be taken to limit the scope of claimed subject matter or their equivalents.

In the following detailed description, numerous specific details are set forth to provide a thorough understanding of claimed subject matter. However, it will be understood by those skilled in the art that claimed subject matter may be practiced without these specific details. In other instances, methods, apparatuses or systems that would be known by one of ordinary skill have not been described in detail so as not to obscure claimed subject matter.

Reference throughout this specification to “one embodiment” or “an embodiment” may mean that a particular feature, structure, or characteristic described in connection with a particular embodiment may be included in at least one embodiment of claimed subject matter. Thus, appearances of the phrase “in one embodiment” or “an embodiment” in various places throughout this specification are not necessarily intended to refer to the same embodiment or to any one particular embodiment described. Furthermore, it is to be understood that particular features, structures, or characteristics described may be combined in various ways in one or more embodiments. In general, of course, these and other issues may vary with the particular context of usage. Therefore, the particular context of the description or the usage of these terms may provide helpful guidance regarding inferences to be drawn for that context.

Likewise, the terms, “and,” “and/or,” and “or” as used herein may include a variety of meanings that also is expected to depend at least in part upon the context in which such terms are used. Typically, “or” as well as “and/or” if used to associate a list, such as A, B or C, is intended to mean A, B, and C, here used in the inclusive sense, as well as A, B or C, here used in the exclusive sense. In addition, the term “one or more” as used herein may be used to describe any feature, structure, or characteristic in the singular or may be used to describe some combination of features, structures or characteristics. Though, it should be noted that this is merely an illustrative example and claimed subject matter is not limited to this example.

Some portions of the detailed description which follow are presented in terms of algorithms or symbolic representations of operations on data bits or binary digital signals stored within a computing platform memory, such as a computer memory. These algorithmic descriptions or representations are examples of techniques used by those of ordinary skill in the data processing arts to convey the substance of their work to others skilled in the art. An algorithm here, and generally, is considered to be a self-consistent sequence of operations or similar processing leading to a desired result. In this context, operations or processing involve physical manipulation of physical quantities. Typically, although not necessarily, such quantities may take the form of electrical or magnetic signals capable of being stored, transferred, combined, compared or otherwise manipulated. It has proven convenient at times, principally for reasons of common usage, to refer to such signals as bits, data, values, elements, symbols, characters, terms, numbers, numerals or the like. It should be understood, however, that all of these and similar terms are to be associated with appropriate physical quantities and are merely convenient labels. Unless specifically stated otherwise, as apparent from the following discussion, it is appreciated that throughout this specification discussions utilizing terms such as “processing,” “computing,” “calculating,” “determining” or the like refer to actions or processes of a computing platform, such as a computer or a similar electronic computing device, that manipulates or transforms data represented as physical electronic or magnetic quantities within memories, registers, or other information storage devices, transmission devices, or display devices of the computing platform. Further, unless specifically stated otherwise, processes described herein, with reference to flow diagrams or otherwise, may also be executed and/or controlled, in whole or in part, by such a computing platform.

As discussed above, as non-volatile memories, such as Flash memories, increase in storage capacity and as storage cell geometries decrease, issues related to error correction/detection and device longevity may become more prominent. As used herein, the term “non-volatile memory” may relate to a memory that does not need power to maintain information stored in the memory. Non-volatile memories may be utilized in a very wide range of electronic device types, including, but not limited to, digital cameras, cellular telephones, personal digital assistants, portable navigation devices, portable music players, notebook computers, desktop computers, etc., to name but a few examples. Non-volatile memories may also be employed, for example, in solid-state storage devices such as memory sticks, Universal Serial Bus (USB) flash drives, memory cards, etc., again, to name but a few examples.

Flash memory is a popular type of non-volatile memory that may be characterized at least in part by the ability to be electrically erasable and programmable. Erase operations may occur on a per-block basis, where a block may comprise a plurality of storage locations. For merely one example, a block may comprise 16 kB of storage. For some flash memories, a block may comprise a number of pages. Continuing the current example, a flash memory with a block size of 16 kB may comprise 32 pages with 512 bytes per page. Flash memories may also comprise several bytes of storage space per page that may be utilized for error detection and correction information, such as, for example, a checksum. Of course, these are merely example characteristics of a flash memory, and the scope of claimed subject matter is not limited in these respects.

Flash memories may also be characterized, at least in part, by the gradual deterioration of storage cells as they undergo erase operations, resulting in an inability to correctly and reliably store data after a number of erase operations. Because erase operations may be performed on a per-block basis, blocks that are erased most often are most likely to become unreliable first. The number of erase operations that a block may undergo before experiencing reliability issues may vary widely, depending on any of a number of possible factors. However, for one example flash memory, the number of write-erase cycles that may be performed before a block begins to experience reliability issues may be about 100,000, although of course this number is merely an example.

As the densities of flash memories increase, the number of errors in reading and writing data may increase, and data retention errors may also increase. To accommodate the possibility of increased errors, more powerful error correction and detection procedures may be utilized, perhaps requiring an increased number of bytes per page to be set aside in the flash memory for error detection and correction checksum information, resulting in increased overhead. Further, as the blocks age as they undergo erase operations over time, the storage locations utilized by the error detection and correction information may become unreliable.

FIG. 1 is a block diagram of an example information storage system 100 comprising a primary memory component 110 and a secondary memory component 120. The two memory components for this example are coupled to a microcontroller 130, which may manage accesses to primary memory 110 from external components or devices. Microcontroller 130 for this example embodiment is coupled to primary memory 110 and secondary memory 130 by one or more address lines, control lines, and data lines. For one embodiment, such as that depicted in FIG. 1, microcontroller 130 may communicate with primary memory 110 and secondary memory 130 via separate sets of address, control, and data lines, although the scope of claimed subject matter is not limited in this respect. For one or more embodiments, primary memory 110 may comprise a flash memory. For an embodiment, primary memory 110 may comprise a NAND flash memory device, although the scope of claimed subject matter is not limited in this respect. For example, other embodiments may incorporate a NOR flash memory. Also for one or more embodiments, secondary memory 120 may comprise a phase-change memory (PCM) component, although the scope of claimed subject matter is not limited in this respect.

The term “PCM memory” as used herein relates to a type of non-volatile memory that is based on the characteristics of chalcogenide glass that can be switched between crystalline and amorphous states with an application of heat. PCM memory devices may also be referred to as PRAM devices. PCM memory differs from flash memory in a number of ways. Once difference is that with PCM memory single bits may be changed to either 1 or 0 without needing to first erase a block of cells. Also, while a small amount of degradation may occur over time, the amount of degradation is generally considered to be several orders of magnitude less than that of flash memories.

For an embodiment, secondary memory 120 may contain error detection and correction information related to blocks of information stored in primary memory 110. In providing a separate memory device for storing error detection and correction information, it may be possible to devote more bits of information to error detection and correction schemes, thereby providing increased ability to detect and correct errors. Further, by locating the error detection and correction information on secondary memory 120, the error detection and correction information may not be subject to the more easily deteriorating primary memory. Further, the increased ability to detect and correct errors may provide for a greater number of erase cycles in primary memory 110 before the number of errors grows too large to be adequately handled by the increased ability to detect and correct errors made possible by the larger number of bits dedicated to the task.

For an embodiment, secondary memory 120 may be smaller than primary memory 110. The size of secondary memory 120 may be selected according to the level of error correction and detection desired, for example. Also, although example embodiments described herein utilize PCM memory for secondary memory 120, the scope of claimed subject matter is not limited in this respect.

For one or more embodiments, error detection and correction operations may be performed by microcontroller 130. Microcontroller 130, for one or more embodiments, may comprise any of a range of device types capable of executing instructions. Also, for the example embodiment depicted in FIG. 1, microcontroller 130 may provide an interface to other devices or components within an electronic device. For example, if system 100 is implemented in a notebook computer, system logic components of the computer may communicate with primary memory 110 through microcontroller 130. Similarly, if system 100 comprises a USB flash drive, microcontroller 130 may be coupled to an external connector, so that if the flash drive is inserted into a host computing platform or other device, microcontroller 130 becomes connected to that host computing platform, and the host computing platform may access primary memory 110 through microcontroller 130. In addition to managing access to primary memory 110 and performing error detection and correction operations, microcontroller 130 may also perform wear-leveling operations, as discussed below. For some embodiments, information utilized in wear-leveling operations may be stored in a secondary memory, as also discussed below.

Further, information storage system 100 may comprise any of a wide range of device types that utilize non-volatile memory. For example, information storage system 100 may comprise a solid-state storage device such as a USB flash drive. Information storage system 100 may be embedded in a digital camera or in a notebook computer, to name a couple of additional examples. Other possible device types may include, but are not limited to, cellular phones, personal digital assistants, desktop computers, memory cards, memory sticks, etc. However, these are merely examples of device types that may incorporate a system such as information storage system 100, and the scope of claimed subject matter is not limited in this respect.

FIG. 2 is a block diagram of an example embodiment of a computing platform 200. The example of FIG. 2 depicts a couple of different possibilities for embodiments of information storage systems such as that described above in connection with FIG. 1. For the present example, Flash drive 290 and non-volatile memory 280 may comprise information storage systems in accordance with embodiments described herein, for example as described above for storage system 100. Computing platform 200 merely represents one possible computing platform configuration, and the scope of claimed subject matter is not limited in this respect. Computing platform 200 may comprise a central processing unit (CPU) 210 and a memory controller hub 220 coupled to CPU 210. Memory controller hub 220 is further coupled to a system memory 230, to a graphics processing unit (GPU) 250, and to an input/output hub 240. GPU 250 is further coupled to a display device 260, which may comprise a CRT display, a flat panel LCD display, or other type of display device. Also coupled to GPU 250 is a graphics memory 270. For this example embodiment, graphics memory 270 may be coupled to GPU 250 via a parallel data interface or interconnect, and input/output hub 240 may be coupled to memory controller hub 220 via a serial data interface or interconnect.

Further, for the example embodiment depicted in FIG. 2, input/output hub 240 may be coupled to non-volatile memory 280, and may further be coupled to Flash drive 290, which, for the embodiment depicted in FIG. 2, may comprise a USB Flash drive inserted into a USB port in system 200 (not shown). As mentioned above, Flash drive 290 may comprise an information storage system in accordance with the example embodiment depicted in FIG. 1. Also for an embodiment, non-volatile memory 280 may also comprise an information storage system in accordance with the example embodiment depicted in FIG. 1. System memory 230 may, for an embodiment, have stored thereon instructions, that, if executed by CPU 210 may enable the computing platform to perform at least in part error detection and correction operations related to non-volatile memory 280, although the scope of claimed subject matter is not limited in this respect. Also, Flash drive 280 may incorporate a microcontroller that may be enabled to perform error detection and correction operations, for one or more embodiments.

The scope of claimed subject matter is not limited to any particular error detection technique, nor is it limited to any particular error correction technique. Any of a wide range of error detection and correction techniques may be utilized in one or more embodiments. “Error detection” may relate to the ability to detect the presence of errors caused by noise or other signal integrity issues during transmission from a transmitter to a receiver, and may also relate to the detection of data retention errors, that is, errors that occur after the data is received at the receiving device. “Error correction” may relate to the ability to reconstruct the original, error free data given the corrupted data and its associated error correction code. As mentioned previously, for one or more embodiments, data may be stored in a primary non-volatile memory component, and the error correction information associated with the data may be stored in a secondary non-volatile memory. The discussion below in connection with FIGS. 3 and 4 describe some example embodiments for storing error correction information in a secondary memory component.

The term “computing platform” as used herein refers to a system or a device that includes the ability to process or store data in the form of signals. Thus, a computing platform, in this context, may comprise hardware, software, firmware or any combination thereof. For one or more embodiments, a computing platform may comprise any of a wide range of digital electronic devices, including, but not limited to, personal desktop or notebook computers, high-definition televisions, digital versatile disc (DVD) players or recorders, game consoles, satellite television receivers, cellular telephones, personal digital assistants, mobile audio or video playback or recording devices, and so on. Further, unless specifically stated otherwise, a process as described herein, with reference to flow diagrams or otherwise, may also be executed or controlled, in whole or in part, by a computing platform. Computing platform 200 is merely one example of a computing platform, and the scope of claimed subject matter is not limited in this respect.

FIG. 3 is a diagram depicting an array of storage locations for primary memory 110 and secondary memory 120. For one or more embodiments, a dedication portion 303 of secondary memory 120 may be associated with a chunk 301 of primary memory 110. For an embodiment, there may be a one-to-one relationship between chunk 301 and dedication portion 303.

For an embodiment, chunk 301 may comprise one page from a block of memory. A block of memory may comprise a plurality of storage locations, wherein the storage locations individually may contain a byte or more of data. As indicated in an example above, a block of memory may comprise, for an embodiment, 16 kB, and may be organized into 32 pages with 512 bytes per page. Of course, this is merely an example block size and an example organization for the block, and the scope of claimed subject matter is not limited in these respects. Chunk 301, therefore, for this example embodiment, may comprise 512 bytes, although again, the scope of claimed subject matter is not limited in this respect. Dedicated portion 303 may comprise any of a range of sizes, depending on the number of bits required to enable a desired level of error detection and correction. For the present example embodiment, there is a single dedicated portion in the secondary memory associated with chunk 301. As will be seen in the discussion below in connection with FIG. 5, the scope of claimed subject matter is not limited to a single dedicated portion of the secondary memory associated with a chunk of the primary memory.

FIG. 4 is a flow diagram of an example embodiment of a method for storing error correction information. At block 410, data may be stored in one or more of a plurality of blocks of storage locations in a first non-volatile memory component. At block 420, error correction information related to the one or more of the plurality of blocks of storage locations may be stored in a second non-volatile memory component. Embodiments in accordance with claimed subject matter may include all of, more than, or less than blocks 410 and 420. Further, the order of blocks 410 and 420 is merely an example order, and the scope of claimed subject matter is not limited in this respect.

For the example embodiment of FIG. 4, the first non-volatile memory may comprise a NAND Flash memory. The second non-volatile memory for the example may comprise a PCM memory. However, the scope of claimed subject matter is not limited to these particular memory device types. For example, the first non-volatile memory component may comprise a NOR flash memory component for an embodiment. Also, for one or more embodiments, the second memory component may comprise any of a range of device types including, but not limited to, dynamic random access memory (DRAM), Flash NOR, Flash NAND, and PCM Flash, to name but a few examples.

As discussed above, PCM memory has a feature of being able to re-write a single bit of information without first requiring an erase operation. PCM memory further comprises non-volatile memory, wherein data may be retained even in the absence of applied power. The ability to perform write operations without needing to perform erase operations allows for read and write operations that are faster than those for NAND and NOR memories.

As also mentioned above, PCM memory may be more reliable than other non-volatile memory types. The increased reliability and performance of PCM memory may make PCM memory a good choice to act as a secondary memory to store error correction information related to a primary memory.

Write operations to a PCM memory may take one of a couple of forms. In an embodiment, in a “program” mode of operation, a bit value of “1” denotes a mask, and the contents of the field for that bit are not changed. A bit value of “0” indicates that the contents of the field for that bit are to be modified. Also for an embodiment, in an “overwrite” mode of operation, all of the bits are considered to carry information to be written.

For one or more embodiments, an additional “program” mode of operation may be implemented. For this additional program mode, a bit value of “0” serves as a mask, and the contents of the field for that bit are not changed. A bit value of “1” indicates that the content of the field of field for that bit are to be modified. For example, if the field has a “0” stored therein, a value of “1” in the incoming data would cause the data in the field to be changed to a “1”. For another example, if the field has stored therein a “1”, a value of “0” in the incoming data would cause the data field to remain at its current value of “0”.

The two “program” modes of operation may be utilized in error detection and correction operations to allow a microcontroller to write partial bytes of data if desired. That is, during a modification of the error correction information stored in the secondary memory, subsets of dedicated portions may be modified with appropriate information without needing to re-program the remaining part of the dedicated portion.

FIG. 5 is a diagram depicting secondary memory 120 with varying levels of error correction information. A first dedicated portion 511 may be associated with a chunk of a primary memory component, such as chunk 301, discussed above. Rather than the static assignment of dedicated portions of secondary memory 120 described above, another technique may be utilized wherein a varying amount of error correction storage space is dedicated to any particular chunk of primary memory. For one or more embodiments, the error correction capability for a single chunk is increased if an error occurs. By increasing the error correction capability in this manner, it may be possible to read the chunk of data correctly in the event of additional errors.

At the start of error correction activities, the plurality of chunks of primary memory are linked to or otherwise associated with corresponding dedicated portions of secondary memory. For example, chunk 301 may be linked to first dedicated portion 511. First dedicated portion 511 for this example is one of a plurality of dedicated portions located within a first section 510 of secondary memory 120. First section 510 for this example may be sufficient in size to enable detection and/or correction of a specified minimum number of errors (min) in the plurality of chunks of primary memory 510. Similarly, the size of individual dedicated portions, such as portion 511, may be determined according to a minimum number of bits required to protect against a specified minimum number of errors. The total size of first section 510, for the present example, may be determined by multiplying the total number of chunks in primary memory by the number of bits per chunk required to detect and correct the specified number of minimum errors. Note that in selecting the minimum size of first section 510 in this manner, it is ensured that enough secondary memory is set aside so that the specified minimum number of errors may be detected and corrected for all of the chunks of primary memory 110. The remaining portion of secondary memory 120 may be divided to produce a second section 520 and the remainder. Second section 520 for this embodiment may be dedicated to storage of sufficient bits to be able to detect and correct an additional number “A” of errors. In other words, for the particular chunk 301 of primary memory 110, the combined number of bits in first dedicated portion 511 and second dedicated portion 521 is sufficient to detect and correct min+A errors. Second dedicated portion 521 may be linked to first dedicated portion 511 by way of a pointer, in an embodiment, stored along with error correction information in first dedicated portion 511. In another embodiment, relationships between dedicated portions may be maintained in a table stored elsewhere in either primary memory 110 or secondary memory 120.

If more bits are desired for error detection and correction than can be provided by first section 510 and second section 520, the remaining portion of secondary memory 120 may be divided in a manner similar to that discussed above in connection with second section 520. For example, an n^(th) section 530 may be set apart to provide for the detection and correction of min+(n−1)Δ errors. A last section 540, along with the other dedicated sections of secondary memory 120, is dedicated to the detection and correction of a maximum (max) number of errors. Of course, the maximum number of errors may be bound by the particular error detection and correction algorithm utilized, the size of primary memory 110, and the size of secondary memory 120. For one or more embodiments, and as mentioned above, all of the chunks of primary memory 110 may be associated with a dedicated portion within first section 510 of secondary memory 120. Thus, all of primary memory 110 may be assured of the detection and correction of the specified minimum number of errors. Also, for an embodiment, links or associations to other dedicated portions within sections 520, 530, or 540, for example, may be determined as errors are detected for various chunks of primary memory 110. Thus, for some chunks of primary memory 110, the error detection and correction algorithm may make use of increasing numbers of bits of error correction information for those chunks experiencing greater numbers of errors. For example, if relatively large numbers of errors are found within chunk 301, first dedicated portion 511, second dedicated portion 521, n^(th) dedicated portion 531, and last dedicated portion 541 may all be utilized to store error correction information associated with chunk 301.

As mentioned previously, for one or more embodiments, some chunks of primary memory 110 may have greater error detection and correction capabilities than other chunks, depending on the allotment of dedicated portions within the various levels of sections in secondary memory. As also mentioned previously, it may be desirable to track which chunks have greater than minimum error correction capability and at which address the additional bits of error correction information are stored. For an embodiment, this information may be stored in spare areas of primary memory 110 that might otherwise have been used for error correction information in the absence of a secondary memory.

For another embodiment, the spare areas of primary memory noted above may be utilized to store error correction information sufficient to detect and correct minimum amounts of errors, and the secondary memory may be utilized to store additional error correction information to increase the error detecting and correcting capabilities for associated chunks of primary memory.

In yet another embodiment, the spare areas of primary memory may be utilized as the last dedicated portions for error correction information storage, and the secondary memory may be utilized for the other levels of sections of dedicated portions.

Of course, the above techniques for organizing error detection and correction information storage are merely examples, and the scope of claimed subject matter is not limited in these respects. Also, embodiments in accordance with claimed subject matter are not limited to any particular error detection and/or correction algorithm. Example error correction codes that may be utilized may include, but are not limited to, BCH codes and Reed-Solomon codes, to name but a couple of examples.

Another aspect to increasing the reliability of Flash memory involves “wear leveling.” Wear leveling, in general, may comprise a function that allows for uniform usage of the blocks of a memory device. For Flash memory such as NAND memory, wear leveling algorithms may enhance the reliability of the memory and increase the life-span of individual blocks. For one or more embodiments, static and/or dynamic wear-leveling algorithms may be utilized. In the case of dynamic wear leveling, incoming data may be written to free blocks in order to spread the usage of flash blocks uniformly over the whole free flash space, upon the arrival of new fresh data.

For static wear-leveling, all blocks of memory may be involved in leveling operations, including blocks of memory whose data never or rarely changes. Such blocks may have their contents copied to another block so that the original block can be used for more frequently-changing data. Static wear leveling operations may be triggered if the difference between the maximum and the minimum number of write/erase cycles per block reaches a specified threshold. In order to execute static wear-leveling operations, information related to the “ages” of the various blocks of memory may be stored. One embodiment for storing wear-leveling information is discussed below.

FIG. 6 is a block diagram of an information storage system 600 comprising a NAND memory 610 and a PCM memory 620. Also included in system 600 for this example embodiment is a microcontroller 630. Microcontroller 630 may, for this example, perform the wear-leveling operations described herein at least in part by executing instructions stored on secondary PCM memory 620, although the scope of claimed subject matter is not limited in this respect.

As depicted in FIG. 6, NAND memory 610 comprises a plurality of blocks. PCM memory 620 for this example embodiment contains a plurality of storage locations for storing wear-leveling information 625. The blocks of wear-leveling information 625 are associated with the plurality of blocks of NAND memory 610. Wear-leveling information 625 for an embodiment may comprise the number of times a particular block of NAND memory 610 has been erased. Also for an embodiment, if a block is erased, that block's age counter may be incremented. The increment may be made by writing a bit of information to the PCM memory. Note that with PCM memory, there is no need to erase a block before writing to it. By maintaining the wear-leveling information in a secondary memory, such as PCM memory 620, the wear-leveling information is not subject to the long-term reliability issues of the NAND memory, and more space may be available on the primary memory. Further, the use of secondary memory to store wear-leveling information related to the primary memory avoids the situation of needing to store the wear-leveling information in the primary memory, which would result in a loss of primary storage locations and would further result in an increase in overhead. Using the wear-leveling techniques described herein, the mean age of the physical NAND blocks of primary memory 610 may be maintained approximately constant.

For another embodiment, error correction information and wear-leveling information related to a primary flash memory may both be stored on a secondary memory such as, for this example, a PCM memory. For this embodiment, wear-leveling operations may take advantage of the information on failed bits to increase a block's age, thereby extending the useful life of the primary flash memory.

In the preceding description, various aspects of claimed subject matter have been described. For purposes of explanation, systems or configurations were set forth to provide an understanding of claimed subject matter. However, claimed subject matter may be practiced without those specific details. In other instances, well-known features were omitted or simplified so as not to obscure claimed subject matter. While certain features have been illustrated or described herein, many modifications, substitutions, changes or equivalents will now occur to those skilled in the art. It is, therefore, to be understood that the appended claims are intended to cover all such modifications or changes as fall within the true spirit of claimed subject matter. 

What is claimed is:
 1. An apparatus comprising: a first non-volatile memory component comprising blocks configured to store data; and a second memory component configured to store error correction information related to the blocks storing the data, wherein the first memory component and the second memory component are of different types.
 2. The apparatus of claim 1, wherein the first non-volatile memory component comprises a flash memory component.
 3. The apparatus of claim 2, wherein the second memory component comprises a phase-change memory (PCM) component.
 4. The apparatus of claim 1, wherein the second memory component is selected from the group consisting of: dynamic random access memory (DRAM), flash NOR, flash NAND, and PCM flash.
 5. The apparatus of claim 1, wherein the first non-volatile memory component experiences a first rate of degradation and the second memory component experiences a second rate of degradation, wherein the second rate of degradation is less than the first rate of degradation.
 6. The apparatus of claim 1, wherein the first non-volatile memory component is configured to perform erase operations on a per-block basis and the second memory component is not configured to perform erase operations on a per-block basis.
 7. The apparatus of claim 1, wherein the second memory component is configured to rewrite single bits of information without an erase operation.
 8. The apparatus of claim 1, wherein the first non-volatile memory component has a first memory capacity and the second memory component has a second memory capacity, wherein the second memory capacity is smaller than the first memory capacity.
 9. The apparatus of claim 1, further comprising a microcontroller coupled to the first memory component and to the second memory component.
 10. The apparatus of claim 9, wherein the microcontroller is configured to perform wear-leveling operations on the first non-volatile memory component using information stored in the second memory component.
 11. The apparatus of claim 1, wherein the second memory component comprises portions associated with blocks of the first non-volatile memory component with a one-to-one correspondence.
 12. The apparatus of claim 11, wherein each block of the blocks of the first non-volatile memory component comprises a plurality of pages and each portion of the portions of the second memory component has a size configured to enable a desired level of error correction for a block corresponding to the portion.
 13. A method comprising: storing data in at least one block of a plurality of blocks of a first non-volatile memory; and storing, in a second memory, error correction information related to the at least one block of the plurality of blocks, wherein the first memory and the second memory are of different types.
 14. The method of claim 13, wherein said storing the data in the at least one block of the plurality of blocks comprises storing the data in a NAND flash memory.
 15. The method of claim 14, wherein said storing, in the second memory, the error correction information comprises storing the error correction information in a phase-change memory (PCM).
 16. The method of claim 13, wherein said storing, in the second memory, the error correction information comprises storing the error correction information in dynamic random access memory (DRAM), flash NOR, flash NAND, or PCM flash.
 17. The method of claim 13, wherein said storing, in the second memory, the error correction information comprises storing the error correction information in a plurality of portions, wherein each portion of the plurality of portions is associated with a block of a plurality of blocks of the first non-volatile memory with a one-to-one correspondence.
 18. The method of claim 17, further comprising modifying subsets of the error correction information in a portion of the plurality of portions without reprogramming remaining a remaining part of the error detection and correction information in the portion.
 19. The method of claim 13, further comprising performing wear-leveling operations on the first non-volatile memory, at least in part, by executing instructions stored on the second memory.
 20. A system comprising: a computer processor; and a memory device operationally coupled to the computer processor, the memory device comprising: a first non-volatile memory component comprising blocks configured to store data; and a second memory component configured to store error correction information related to the blocks storing the data, wherein the first memory component and the second memory component are of different types. 